WIP: Add support for Certificate verification with CRL #2186
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
You can achieve this though by setting up your own TLS code and using rustls directly. Tonic's tls is meant to be kept slim. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tonic lucks TLS with CRL support.
rustls' ClientCertVerifierBuilder and ServerCertVerifierBuilder support CRL.
Motivation
Enhance tonic implementation to support TLS setup with CRL.
Relates to #1385
Solution
The PR is still a Draft. With respect to feedback, it will be elaborated further in order to achieve readiness.